System and method to provide telematics data on a map display

ABSTRACT

A system and method are disclosed herein to determine an insurance premium discount based on telematics data. The system includes a computer memory and a processor in communication with the computer memory. The computer memory stores data indicative telematics data received from a sensor within a vehicle, including at least one of geo-position information of the vehicle and vehicle kinematics data. The processor is configured to identify safety events and associated safety event locations based on the telematics data. The processor is further configured to display to the driver indications of the safety events on a map display along with indications of safety events associated with other drivers.

CROSS-REFERENCE TO RELATED APPLICATION

This application claims the benefit of U.S. Provisional Application No.61/650,040 entitled “System and Method Associated with Telematics Data”and filed on May 22, 2012. The entire contents of that application areincorporated herein by reference.

FIELD OF THE INVENTION

In general, the invention relates to a computerized system and methodfor providing telematics data on a map display.

BACKGROUND OF THE INVENTION

The insurance industry has begun exploring the use of telematics sensorsand other location-aware devices in motor vehicles as a way ofdetermining driver behavior and, from this, driver risk for the purposesof underwriting, pricing, renewing, and servicing vehicle insurance. Thedevices can capture very high frequency information on location, speed,vehicle handling, vehicle characteristics, and other factors, which canbe used in setting vehicle insurance rates. This data may be used toidentify safety events, such as a moment of relatively highde-acceleration (e.g., a “hard brake” event). The data may also indicateif a vehicle is often driven during times of relatively high risk (e.g.,late at night) and/or at speeds above a pre-determined threshold (e.g.,above 75 miles per hour). It can be difficult to encourage drivers toprovide such data and/or to adjust driving habits in ways that may lowerrisk. The relationships between telematics data (e.g., where and whensafety events occur) and the real world can be difficult for a driver tounderstand. For example, a driver might not realize that he frequentlymakes abrupt stops at a particular intersection.

SUMMARY

Therefore, there is a need in the art for ways to encourage drivers toprovide telematics information and/or modify behaviors so as to reduce alikelihood of accidents and losses. Such measures may, according to someembodiments, use safety events calculated from location informationand/or other vehicle data, such as speed, orientation, and acceleration.Statistical analysis of the data may be used to classify safety eventsas being associated with different intensity levels.

In some embodiments, a processor may receive data indicative oftelematics data collected from a sensor coupled to a vehicle, whereinthe telematics data includes at least one of geo-position informationand kinematics data. The processor may identify safety events andassociated safety event locations based on the telematics data.Indications of the safety events may then be displayed to a driver on amap display and/or a telematics calculator.

According to another aspect, the invention relates to computerizedmethods for carrying out the functionalities described above. Accordingto another aspect, the invention relates to non-transitory computerreadable medium having stored therein instructions for causing aprocessor to carry out the functionalities described above.

BRIEF DESCRIPTION OF THE DRAWINGS

FIG. 1 is an architectural model of a system for determining a discountfor an insurance premium based on telematics data, according to anillustrative embodiment of the invention.

FIG. 2 is a block diagram of a computing system as used in FIG. 1,according to an illustrative embodiment of the invention.

FIG. 3 is a block diagram of a vehicle and a device coupled to thevehicle for collecting telematics data, according to an illustrativeembodiment of the invention.

FIG. 4 illustrates an automobile in accordance with some embodiment ofthe invention.

FIG. 5 is a flowchart of a method according to an illustrativeembodiment of the invention.

FIGS. 6 through 9 illustrate map displays in accordance with someembodiments described herein.

FIGS. 10 and 11 illustrate current telematics displays according to someembodiments.

FIG. 12 illustrates a safety score display according to someembodiments.

FIG. 13 illustrates a likely discount display according to someembodiments.

FIG. 14 illustrates how an insurance premium might change over timeaccording to some embodiments.

FIGS. 15 through 17 are examples of insurance discount calculatordisplays in accordance with some embodiments described herein.

FIG. 18 is a block diagram of an insurance platform provided inaccordance with some embodiments.

FIG. 19 is a tabular portion of a telematics database in accordance withsome embodiments.

DESCRIPTION OF CERTAIN ILLUSTRATIVE EMBODIMENTS

To provide an overall understanding of the invention, certainillustrative embodiments will now be described, including systems andmethods for determining an insurance premium discount using geo-spatialinformation and/or other telematics data. However, it will be understoodby one of ordinary skill in the art that the systems and methodsdescribed herein may be adapted and modified as is appropriate for theapplication being addressed and that the systems and methods describedherein may be employed in other suitable applications, and that suchother additions and modifications will not depart from the scopethereof.

FIG. 1 is a block diagram of a system 100 for determining a discount foran insurance premium based on telematics data according to anillustrative embodiment. The system 100 uses data collected alongmultiple trips traveled by a vehicle, including, for example, speedinginformation, time of day information, and/or safety event information.An insurance company may use route data, such as Global PositioningSatellite (“GPS”) latitude and longitude data, acceleration/decelerationdata, speed data, and/or vehicle orientation data collected along aroute traveled by the vehicle to determine safety associated with adriver and/or a vehicle. With a sufficient amount of data, the insurancecompany can calculate a level of risk score for the driver based on, forexample, the driver's driving habits. The insurance company can use thescore for setting or adjusting a discount value to be applied to aninsurance premium. In some implementations, a score or discount isdetermined by a third party data processing service. In addition, thescore or discount may be set by an underwriter, which may be a part ofthe insurance company or otherwise affiliated with or in a third partyarrangement with the insurance company. According to any embodimentsdescribed here, a score might be used to determine a premium price, apremium adjustment, and/or any other benefit that may be associated withan insurance policy (e.g., a decreased deductable value or increasedoverall coverage amount).

The system 100 includes one or more vehicles 102, each having a datacollection device 104. The vehicle 102 may be an automobile, motorcycle,truck, bus, watercraft, aircraft, or any other vehicle operated by adriver. A data collection device 104 is coupled to a vehicle 102 forcollecting data about the vehicle's location, movements, or otherinformation that can be used to determine risk scores. For vehicles withmultiple drivers, the data may be associated with the vehicle itself orwith the individual drivers. The data collection device 104 may bepositioned inside the vehicle 102, attached to the outside of thevehicle 102, or integrated into the vehicle 102. The data collectiondevice 104 is in communication with an insurance company system 108 overa communication network 150. The data collection device 104 maycommunicate with the insurance company system 108 though a wirelessnetwork such as a cellular network or using a wireless Internetconnection. In general, the data collection device 104 can be anycomputing device or plurality of computing devices in cooperation havinga data collection sensor (e.g., an antenna or an accelerometer), aprocessor, a memory, and a means for transmitting the collected data.The customer vehicle 102 or data collection device 104 may include anantenna for receiving signals from Global Navigation Satellite System(“GNSS”) satellites, numbered 1 through “n” in FIG. 1. In oneimplementation, the data collection device 104 is also configured toprocess the collected data. In some embodiments, the data processingprotects the driver's privacy by encrypting the data, removing locationinformation, producing summary information, or taking other measures toreduce the likelihood that location information, speed information, orother sensitive information are received by the insurance company orthird parties.

In some embodiments, rather than sending collected data directly to theinsurance company system 108, the data collection device 104 sendscollected data to a data processing service 106, which processes thedata to determine a risk score and/or an appropriate premium discountfor a driver that is then sent to the insurance company system 108. Thiscan help protect a driver's privacy, since the insurance company doesnot get detailed data about a driver's location, but only receivessummary information. Using a data processing service 106 is in someimplementations also preferable to having the data collection device 104process data to output a risk score because it reduces the processingpower needed by data collection device 104 and because using a thirdparty data processing service 106 may also make it more difficult fordrivers to tamper with the data. The data processing service 106 canperform additional monitoring functions, such as vehicle securitymonitoring or providing location-based alerts (e.g., alerting a parentor employer when a vehicle travels an unusual path) and/or speed alerts.Note that an insurance company might received detailed reports from thethird party data processing service 106, summary reports (with certaindetails removed), and/or supplemented information (e.g., includinginformation from one or more public databases).

The insurance company system 108 includes a plurality of applicationservers 112, a plurality of load balancing proxy servers 114, aninsurance company database 116, a processing unit 120, and companyterminal 122. These computing devices are connected by a local areanetwork 124.

The application servers 112 are responsible for interacting with thedata collection device 104 and/or the data processing service 106. Thedata exchange between the insurance company system 108 and datacollection device 104 and/or data processing service 106 can utilizepush and pull technologies where the application servers 112 of theinsurance company system 108 can act as both a server and client forpushing data to the data processing service 106 (e.g., which vehicles tomonitor, when to stop data collection, rules for monitoring servicesrequested by the customer) and for pulling data from the data processingservice 106. The application servers 112 or other servers of theinsurance company system 108 can request to receive periodic data feedsfrom the data collection device 104 and/or data processing service 106.The communication between the application servers 112 and the dataprocessing service 106 can follow various known communication protocols,such as TCP/IP. Alternatively, the application servers 112 and dataprocessing service 106 can communicate with each other wirelessly, e.g.,via cellular communication, Wi-Fi, Wi-Max, or other wirelesscommunications technologies or combination of wired or wirelesschannels. The load balancing proxy servers 114 operate to distribute theload among application servers 112.

The insurance company database 116 stores information about vehicularinsurance policies. For each insurance policy, the database 116 includesfor example and without limitation, the following data fields: policycoverage, a risk rating, policy limits, deductibles, the agentresponsible for the sale or renewal, the date of purchase, dates ofsubsequent renewals, product and price of product sold, applicableautomation services (for example, electronic billing, automaticelectronic funds transfers, centralized customer service planselections, etc.), customer information, customer payment history, orderivations thereof. Note that any of the embodiments described hereinmight be associated with existing insurance policies, newly issuedinsurance policies, and/or policies that have not yet been issued (e.g.,during a trial phase before a policy is issued). According to someembodiments, information collected during a trial period may influence adiscount or other benefit that is eventually associated with aninsurance policy.

The processing unit 120 is configured for determining the price of aninsurance premium based on a risk rating for a driver or vehicle. Theprocessing unit 120 may comprise multiple separate processors, such as arisk or safety processor, which may calculates a safety rating from rawor processed data from the data collection device 104 or data processingservice 106 over the communications network 150; and a business logicprocessor, which determines a premium price for a policyholder based on,among other things, a risk score. In some embodiments, insurance premiumprices or information for making insurance pricing determinations may begenerated by a third-party underwriter, which is separate from theinsurance company system 108. An exemplary implementation of a computingdevice for use in the processing unit 120 is discussed in greater detailin relation to FIG. 2.

The company terminals 122 provide various user interfaces to insurancecompany employees to interact with the processing system 120. Theinterfaces include, without limitation, interfaces to review telematicsdata, or risk ratings; to retrieve data related to insurance policies;to manually adjust a risk rating; and to manually adjust premiumpricing. In some instances, different users may be given differentaccess privileges. For example, marketing employees may only be able toretrieve information on insurance policies but not make any changes todata. Such interfaces may be integrated into one or more websites formanaging the insurance company system 108 presented by the applicationservers 112, or they may be integrated into thin or thick softwareclients or stand alone software. The company terminals 122 can be anycomputing devices suitable for carrying out the processes describedabove, including personal computers, laptop computers, tablet computers,smartphones, servers, and other computing devices.

The user terminal 130 provides various user interfaces to customers tointeract with the insurance company system 108 over the communicationsnetwork 150. Potential customers can use user terminals 130 to retrievepolicy and pricing information for insurance policies offered by theinsurance company. Customers can enter information pertaining to changesin their insurance policy, e.g., changes in policy coverage, addition orsubtraction of drivers, addition or subtraction of vehicles, relocation,mileage information, etc. Customers can also use the user terminal 130for a pay-as-you-go insurance policy in which customers purchaseinsurance by the trip or mile.

In some embodiments, the data collection device 104 may not becontinually connected to the insurance company system 108 via thenetwork 150. For example, the data collection device 104 may beconfigured to temporarily store data if the data collection device 104becomes disconnected from the network, like when it travels out of rangeof cellular towers. When the connection is restored, the data collectiondevice 104 can then transmit the temporarily stored data to theinsurance company system 108. The data collection device 104 mayalternatively be configured to connect to the communications network 150through a user's home Wi-Fi network. In this case, the data collectiondevice 104 stores trip data until it returns to the vicinity of theuser's home, connects to the user's wireless network, and sends thedata. In some embodiments, the data collection device 104 is notconnected to the network 150 at all, but rather, data collected istransmitted to the insurance company though other means. For example, acustomer can receive a data collection device 104 from the insurancecompany, couple the device 104 to his car for a set period of time ornumber of miles, and then either mail the device 104 with the collecteddata to the insurance company system 108 or extract and send thecollected data to the insurance company system 108 via mail, email, orthough a website.

FIG. 2 is a block diagram of a computing device 200 used for carryingout at least one of an insurance premium discount determination andbusiness logic processing described in relation to FIG. 1, according toan illustrative embodiment of the invention. The computing device 200comprises at least one network interface unit 204, an input/outputcontroller 206, system memory 208, and one or more data storage devices214. The system memory 208 includes at least one Random Access Memory(“RAM”) 210 and at least one Read-Only Memory (“ROM”) 212. All of theseelements are in communication with a Central Processing Unit (“CPU”) 202to facilitate the operation of the computing device 200. The computingdevice 200 may be configured in many different ways. For example, thecomputing device 200 may be a conventional standalone computer oralternatively, the functions of computing device 200 may be distributedacross multiple computer systems and architectures. The computing device200 may be configured to perform some or all of the insurance premiumdiscount determination and business logic processing, or these functionsmay be distributed across multiple computer systems and architectures.In the embodiment shown in FIG. 2, the computing device 200 is linked,via network 150 or local network 124, to other servers or systems housedby the insurance company system 108, such as the load balancing server114, and/or the application servers 112.

The computing device 200 may be configured in a distributedarchitecture, wherein databases and processors are housed in separateunits or locations. The computing device 200 may also be implemented asa server located either on site near the insurance company system 108,or it may be accessed remotely by the insurance company system 108. Somesuch units perform primary processing functions and contain at a minimuma general controller or a processor 202 and a system memory 208. In suchan embodiment, each of these units is attached via the network interfaceunit 204 to a communications hub or port (not shown) that serves as aprimary communication link with other servers, client or user computersand other related devices. The communications hub or port may haveminimal processing capability itself, serving primarily as acommunications router. A variety of communications protocols may be partof the system, including, but not limited to: Ethernet, SAP, SAS™, ATP,BLUETOOTH™, GSM and TCP/IP.

The CPU 202 comprises a processor, such as one or more conventionalmicroprocessors and one or more supplementary co-processors such as mathco-processors for offloading workload from the CPU 202. The CPU 202 isin communication with the network interface unit 204 and theinput/output controller 206, through which the CPU 202 communicates withother devices such as other servers, user terminals, or devices. Thenetwork interface unit 204 and/or the input/output controller 206 mayinclude multiple communication channels for simultaneous communicationwith, for example, other processors, servers or client terminals.Devices in communication with each other need not be continuallytransmitting to each other. On the contrary, such devices need onlytransmit to each other as necessary, may actually refrain fromexchanging data most of the time, and may require several steps to beperformed to establish a communication link between the devices.

The CPU 202 is also in communication with the data storage device 214.The data storage device 214 may comprise an appropriate combination ofmagnetic, optical and/or semiconductor memory, and may include, forexample, RAM, ROM, flash drive, an optical disc such as a compact discand/or a hard disk or drive. The CPU 202 and the data storage device 214each may be, for example, located entirely within a single computer orother computing device; or connected to each other by a communicationmedium, such as a USB port, serial port cable, a coaxial cable, anEthernet type cable, a telephone line, a radio frequency transceiver orother similar wireless or wired medium or combination of the foregoing.For example, the CPU 202 may be connected to the data storage device 214via the network interface unit 204.

The CPU 202 may be configured to perform one or more particularprocessing functions. For example, the computing device 200 may beconfigured for calculating a risk or safety score for a driver orvehicle. The same computing device 200 or another similar computingdevice may be configured for calculating an aggregate risk rating basedon multiple safety scores (e.g., associated with different clusters ofsimilar routes). The same computing device 200 or another similarcomputing device may be configured for calculating an insurance premiumdiscount for a vehicle or driver based at least the risk scores and/orthe safety rating.

The data storage device 214 may store, for example, (i) an operatingsystem 216 for the computing device 200; (ii) one or more applications218 (e.g., computer program code and/or a computer program product)adapted to direct the CPU 202 in accordance with the present invention,and particularly in accordance with the processes described in detailwith regard to the CPU 202; and/or (iii) database(s) 220 adapted tostore information that may be utilized to store information required bythe program. The database(s) 220 may including all or a subset of datastored in insurance company database 116, described above with respectto FIG. 1, as well as additional data, such as formulas or manualadjustments, used in establishing the insurance risk for a vehicle.

The operating system 216 and/or applications 218 may be stored, forexample, in a compressed, an uncompiled and/or an encrypted format, andmay include computer program code. The instructions of the program maybe read into a main memory of the processor from a computer-readablemedium other than the data storage device 214, such as from the ROM 212or from the RAM 210. While execution of sequences of instructions in theprogram causes the CPU 202 to perform the process steps describedherein, hard-wired circuitry may be used in place of, or in combinationwith, software instructions for implementation of the processes of thepresent invention. Thus, embodiments of the present invention are notlimited to any specific combination of hardware and software.

Suitable computer program code may be provided for scoring risk based ontelematics data associated with a plurality of trips taken by a vehicleor driver over a period of time. The program also may include programelements such as an operating system, a database management system and“device drivers” that allow the processor to interface with computerperipheral devices (e.g., a video display, a keyboard, a computer mouse,etc.) via the input/output controller 206.

The term “computer-readable medium” as used herein refers to anynon-transitory medium that provides or participates in providinginstructions to the processor of the computing device (or any otherprocessor of a device described herein) for execution. Such a medium maytake many forms, including but not limited to, non-volatile media andvolatile media. Non-volatile media include, for example, optical,magnetic, or opto-magnetic disks, or integrated circuit memory, such asflash memory. Volatile media include Dynamic Random Access Memory(“DRAM”), which typically constitutes the main memory. Common forms ofcomputer-readable media include, for example, a floppy disk, a flexibledisk, hard disk, magnetic tape, any other magnetic medium, a CD-ROM,DVD, any other optical medium, punch cards, paper tape, any otherphysical medium with patterns of holes, a RAM, a PROM, an EPROM orElectronically Erasable Programmable Read-Only Memory (“EEPROM”), aFLASH-EEPROM, any other memory chip or cartridge, or any othernon-transitory medium from which a computer can read.

Various forms of computer readable media may be involved in carrying oneor more sequences of one or more instructions to the CPU 202 (or anyother processor of a device described herein) for execution. Forexample, the instructions may initially be borne on a magnetic disk of aremote computer (not shown). The remote computer can load theinstructions into its dynamic memory and send the instructions over anEthernet connection, cable line, or even telephone line using a modem. Acommunications device local to a computing device (e.g., a server) canreceive the data on the respective communications line and place thedata on a system bus for the processor. The system bus carries the datato main memory, from which the processor retrieves and executes theinstructions. The instructions received by main memory may optionally bestored in memory either before or after execution by the processor. Inaddition, instructions may be received via a communication port aselectrical, electromagnetic or optical signals, which are exemplaryforms of wireless communications or data streams that carry varioustypes of information.

FIG. 3 is a block diagram of a vehicle 102 having a data collectiondevice 104. As described with regard to FIG. 1, the vehicle 102 may bean automobile, motorcycle, truck, bus, watercraft, aircraft, or anyother vehicle operated by a driver. The vehicle 102 includes a vehiclecomputer 302, an On-Board Diagnostics (“OBD”) port 304, and vehicletelematics sensors 306. The data collection device 104 is connected tothe vehicle 102 via an OBD port connector 322 connected to the OBD port304 to receive telematics data and other information. The datacollection device 104 includes a CPU 310, a GNSS receiver 312, anaccelerometer 314, memory 316, a user interface 318, and a wirelesscommunications device 320. The CPU 310 is in communication with theother elements of the data collection device 104 to facilitate theoperation of the data collection device 104. The CPU can also beconfigured to process data received from the GNSS receiver 312, theaccelerometer 314, and the OBD port connector 322. Data processing mayinclude calculating risk scores, calculating safety ratings, calculatingintermediate values for determining insurance premium discounts, orencrypting data sent by the wireless communications device 320.

The Global Navigation Satellite System (“GNSS”) receiver 312 includes anantenna and associated signal processing circuitry for receiving signalsfrom GNSS satellites, such as the satellites numbered 1 through n inFIG. 1, and determining its location from the signals. GNSS satellitesmay be, for example, GPS, GLONASS, Galileo, or Beidou satellites whichsend time and orbital data from which the data collection device 104 cancalculate its location. In some configurations, the CPU 310 calculatesthe location of the vehicle from data from the receiver 312. The CPU 310can pull location data from the GNSS receiver 312 at set time intervals,such as every 0.1 seconds, 0.2 seconds, 0.5 seconds, 1 second, 2seconds, 7 seconds, or 10 seconds. The CPU 310 sends the location datato the memory 316 along with a time and date stamp indicating when thevehicle was at the location. In some embodiments, the GNSS receiver 312may be part of a separate GNSS device used by the driver for obtainingdriving directions. In this case, the GNSS receiver 312 transmits datato the data collection device 104 though a wired connection or awireless connection, e.g., BLUETOOTH or Wi-Fi.

The accelerometer 314 is a device that measures proper acceleration.Data collected from an accelerometer 314 may include or be used forobtaining the g-force, acceleration, orientation, shock, vibration,jerk, velocity, speed, and/or position of the vehicle. Some or all ofthese types of data are received or calculated by the CPU 310. The CPU310 may collect data at intervals such as every 0.1 seconds, 0.2seconds, 0.5 seconds, 1 second, 2 seconds, 7 seconds, or 10 seconds andstore the data in the memory 316. Each data point is time and datestamped and/or location stamped. In some embodiments, the CPU 310determines intervals between data stored in the memory 316 based ontrends in the data. The rate of data collection may vary based onvehicle behavior; for example, if a driver is travelling along astraight road at a consistent speed, the CPU 310 may save data lessfrequently than if the driver is making frequent turns. In someembodiments, only “exception data” evident of safety events or otherunusual driving behavior is stored. For example, the CPU 310 may onlysave accelerations, decelerations, hard turns, speeds, lane changespeeds, etc. with rates above a certain threshold.

The OBD port connector 322 is used to collect data from the vehiclecomputer 302 and/or vehicle telematics sensors 306 via OBD port 304. Thevehicle computer 302 may provide information about the vehicle's speed,the number of miles traveled, whether the vehicle is running or not,seatbelt usage, airbag deployment, and vehicle diagnostics. Vehiclediagnostics data can be used to determine whether a safety event wascaused by the driver's actions or related to a vehicle malfunction, suchas low tire pressure, low oil pressure, high engine temperature, loss ofpower, and stalling. The vehicle may contain additional telematicssensors 306 for, e.g., vehicle tracking, monitoring gasolineconsumption, and vehicle safety. Data obtained by the data collectiondevice 104 from the vehicle computer 302 and telematics sensors 306 viathe OBD port 304 can supplement or be used instead of data collected bythe GNSS receiver 312 and/or accelerometer 314. In some embodiments, thedata collection device 104 turns on automatically when the vehicle isturned on; the data collection device 104 may be powered by the vehicle102.

The data collection device 104 also includes a wireless communicationsdevice 320 for sending collected data to and receiving commands from thedata processing service 106 and/or insurance company system 108 via thenetwork 150. The data collection device 104 may also be configured forcommunication with the driver or a passenger via user interface 318. Theuser interface 318 includes output components, such as a screen orspeakers, and input components, such as a touch screen, keyboard, ormicrophone. The user interface 318 can output risk data, route summarydata, vehicle diagnostics data, and any data collected from the GNSSreceiver 312, accelerometer 314, and/or OBD port 304. In someembodiments, the data collection device 104 is also a navigation devicethat can calculate and display a route to a destination inputted by theuser.

The vehicle 102 and data collection device 104 may be associated with,for example, an automobile. For example, FIG. 4 illustrates anautomobile 400 in accordance with some embodiment of the invention. Theautomobile 400 includes one or more sensors 410 that may be used tocollect telematics information, such as a GNSS receiver or similardevice. Note that telematics information might instead be associatedwith, for example, a motorcycle, a recreational vehicle, a boat, anairplane, etc.

FIG. 5 is a flowchart of a method 500 for displaying telematics data.The method 500 can be performed by the data collection device 104, thedata processing service 106, the insurance company system 108, or anycombination of these. The method 500 includes the storage of telematicsdata received from a sensor within the vehicle (Step S510).). As usedherein, a sensor may be “within” a vehicle if it is attached to thevehicle (e.g., either inside or outside the body of the vehicle), ispowered by the vehicle, or is otherwise inside or associated with thevehicle. To obtain telematics data, data from receivers and sensors suchas GNSS receiver 312, accelerometer 314, vehicle computer 302, andvehicle telematics sensors 306 may be collected by the data collectiondevice 104 and stored in the memory 306 of the data collection device306 and/or sent to the data processing service 106 or insurance companysystem 108. The method 500 further includes identifying safety eventsand associated safety event locations based on the data indicative ofthe telematics data (Step S520) and displaying to the driver indicationsof the safety events on a map display along with indications of safetyevents associated with other drivers (Step S530). The map display may,for example, further include information from a third party service,such as Google Maps.

According to some embodiments, the safety events displayed on the mapdisplay are associated with telematics data. The telematics data mightinclude, for example, times of day associated with driving, velocitiesassociated with driving, distances associated with driving, weatherinformation, and/or traffic information. Moreover, the insurance companymight identify safety events within the telematics data (e.g., hardbrake events) and/or a severity estimation of the safety events.Moreover, according to some embodiments an insurance platform mightoutput an indication of a suggested driving modification on a mapdisplay along with a discount goal for the insurance premium of theautomobile insurance policy. For example, the driving modification mightinclude a suggested route to a destination to achieve a 15% discount foran insurance premium. According to some embodiments, a suggested drivingmodification may be output to other parties instead of or in addition tothe driver. For example, a suggested modification might be sent to aparent or employer of the driver (e.g., suggesting that the driver spendless time driving over 75 miles per hour). Similarly, information abouttelematics data, including safety events, might be automaticallyforwarded to a community improvement resource (e.g., by sending an emailto a state department of transportation indicating that many hard brakeevents have recently occurred at a particular intersection, perhapsbecause of a new pothole or other driving hazard). According to someembodiments, information about telematics data, including safety events,might be automatically provided via a social network site (e.g., to helpencourage a group of drivers to improve risky driving habits).

According to some embodiments, information about safety events may bedisplayed to a driver on a map display. For example, referring now toFIG. 6, a diagram 650 depicting a user interface 602 is shown. The userinterface 602 may be displayed on device 600 such as a mobile telephone,PDA, personal computer, or the like. For example, the device 600 may bea PC, an iPhone® from Apple, Inc., a BlackBerry® from RIM, a mobilephone using the Google Android® operating system, or the like. The userinterface 602 depicts a portion of a map showing a portion of FairfieldCounty in the State of Connecticut. The user interface 602 may displaythe location of safety events 654, 656 (e.g., locations of rapidde-acceleration, speeding events, etc.) collected in connection with alldrivers who have provided telematics data while driving in that area. Inthis way, a driver may be alerted and take extra precautions whendriving in an area of relatively high risk.

In some embodiments, such as the one depicted in FIG. 6, identifiedsafety events 654, 656 may be associated with a plurality of differentevent types and a substantial number of drivers. For example, safetyevents 654, 656 associated with both hard braking events and excessivespeeding may be displayed in connections with thousands of drivers.According to some embodiments, information about a plurality of safetyevents may be grouped and displayed as a single graphical icon. Forexample, a green circle might indicate that relative few events havebeen recorded for a particular location while a red circle indicatesthat many events have occurred there. Similarly, a number representingan overall number of safety events might be displayed on the interface602. Note that a driver may instead be more interested in his or her ownpersonal safety events. For example, referring now to FIG. 7, a diagram750 depicting a user interface 702 is shown. As before, the userinterface 702 may be displayed on device 700 such as a mobile telephoneand may depict a portion of a map. The user interface 702 may display toa driver the location of safety events 754, 756 (e.g., locations ofrapid de-acceleration) that were a result of his or her driving habits.In this way, a driver may be become aware of unsafe driving habits andadjust his or her behaviors to reduce the risk of an accident.

Note that driving habits and conditions may change over time. Thus,according to some embodiments a driver may interact with a map displayto view safety events associated with a selected range of dates and/ortimes. For example, referring now to FIG. 8, a diagram 850 depictinganother user interface 802 is shown. As before, the user interface 802may be displayed on device 800 such as a mobile telephone and may depicta portion of a map. The user interface 82 may display to a driver thelocation of safety events 854, 856 (e.g., locations of rapidde-acceleration) that occurred during a particular period of time (e.g.,during the prior 24 hours, the prior week, the prior month, the prioryear, etc.). Note that the safety events 854, 856 might be associatedwith the driver's own driving habits or may reflect those of all driverswho have provided telematics data. According to some embodiments, adriver may interact with a “sliding scale” bar to select which period oftime should be used to filter the safety events 854, 856. Note that theidentified safety events 854, 856 may associated with a plurality ofdifferent event types. For example, safety events 854, 786 associatedwith both hard braking events and excessive speeding may be displayed.In this case, different labels (e.g., reflecting event types “1,” “2,”or “3” as illustrated in FIG. 8), icons, or colors may be used todifferentiate event types. Similarly, the safety events 854, 856 may beassociated with different levels of risk or severity (e.g., high,medium, and low intensity events) and these may also be differentiatedon the user interface 802.

In some cases, a driver might be interested in a particular type ofsafety event. According to some embodiments, a selection of a particularevent type may be received from the driver and only indications of thesafety events associated with that particular event type may bedisplayed to the driver on the map display (e.g., only hard brakeevents). For example, referring now to FIG. 9, a diagram 950 depictinganother user interface 902 is shown. As before, the user interface 902may be displayed on device 900 such as a mobile telephone and may depicta portion of a map. The user interface 902 may display to a driver thelocation of safety events 954, 956 (e.g., locations of rapidde-acceleration) that are of particular interest to the driver. In theexample of FIG. 9, the driver has selected to view all high intensitybrake events. Note that the safety events 954, 956 might be associatedwith the driver's own driving habits or may reflect those of all driverswho have provided telematics data. Moreover, selection of a particularevent icon might result in the display of further details about thatparticular event (e.g., the date and time the event occurred). Inaddition to, or instead of, filtering safety events based on event typeor severity, a driver might be able to display events associated with aparticular type of driver or vehicle (e.g., based on age, drivingexperience, gender, etc.). Although information about other drivers'safety events may be displayed on the user interface 902, note that suchinformation may be collected and/or provided in an anonymous fashion.For example, data indicative of telematics data might received by aninsurance company from a third party such that the data that does notidentify particular drivers or vehicles.

In addition to the locations where safety events occurred, a drivermight be interested in his or her overall performance in connection withone or more types of safety events and/or how that performance comparesto others, how that performance is modifying his or her currentinsurance premium discount, etc. FIG. 10 illustrates a currenttelematics display 1000 according to some embodiments. In particular,the display 1000 includes a graphical representation 1010 of informationabout a particular risk variables derived from telematics data which maybe categorized as “below average,” “average,” or “above average” from arisk perspective. The display 1100 also includes a current score (e.g.,calculated at least in part based on the risk variable) and a currentdiscount (e.g., determined based on the current score). Note that thegraphical representation 1010 might instead be a sliding scale, lettergrade (“B+”), or any other type of indication. In addition to, orinstead of, a current number of events per week, a driver might be shownan average number of events for all drivers or for a particular type ofdriver or vehicle (e.g., based on age, driving experience, gender,etc.).

FIG. 11 illustrates another current telematics display 1100 according tosome embodiments. In particular, the display 1100 includes a graphicalrepresentation of information about three different risk variablesderived from telematics data, a current score (e.g., calculated based onthe risk variables) and a current discount (e.g., determined based onthe current score). The current discount might, according to someembodiments, represent the final discount According to some embodiments,the current discount might be calculated in substantially real time orbe recalculated using new data when the driver's safety scores are morelikely change, e.g., if the customer moves, changes jobs, has a child,or retires, or at certain time periods, e.g., every year, every twoyears, every three years, every five years, every ten years, etc. Insome embodiments, both prospective pricing and retroactive pricing areused. For example, a customer being continually monitored can be receivea premium discount for a time period based on one or more past safetyscores, and if the customer's actual score rating for the time periodwas greater than or less than the expected rating, an adjustment may beapplied as appropriate.

By way of example only, a score model might consist of two mainelements: (1) a percentage of time speeding over a threshold value(e.g., 75 miles per hour) and (2) an annualized miles value associatedwith times of day. Each driver's score might, for example, start withfifteen (15) points then be modified by adding speeding points and/orsubtracting time of day mileage by the factors shown below:

For Time of Day:

Risk Level Per Mile Subtraction Risky 0.005 Moderate 0.0025 Low 0.00125Where “risky” is defined as driving between midnight and 4:00 am everyday of the week, “moderate” is driving from 4:00 am to 6:00 am and 9:00pm to midnight every day of the week and 6:00 am to 9:00 am and 3:00 pmto 6:00 pm on weekdays. “Low” risk times may comprise all other times ofthe day.

For Speeding over a Threshold:

% Time Speeding Points >0.75%  0 0.1-0.75% 5 <0.1% 10

In such an example, consider a driver who drives 5,000 annualized miles.Moreover, 4,000 of these miles are driven during moderate risk times ofthe day and 1,000 of these miles are driven during low risk times of theday. Moreover, the driver speeds over the threshold 0.05% of the time.In this case, a safety score might be determined as follows:Safety Score=15+10−(4,000*0.0025+1,000*0.00125)=13.75Rounding this to the nearest whole number and looking it up in arisk/discount table, the driver might receive a 14% discount for his orher insurance premium.

As another example, aggressive driving/hard braking events might beclassified into different intensity or severity levels. For example, atype 1 event might have a threshold of from 340 to 500 milli-g (˜ changein speed or velocity (delta-V) of greater than +/−7.5 mph/sec²) (e.g.,from 14 mph to 25 mph in 1 second). A type 2 event might have athreshold of from 501 to 750 milli-g (˜ change in speed or velocity(delta-V) of greater than +/−11 mph/sec²) (e.g., from 65 mph to 45 mphin 1 second). A type 3 event might have a threshold of 750 milli-g (˜change in speed or velocity (delta-V) of greater than +/−16.5 mph/sec²)(e.g., from 65 mph to 35 mph in 1 second). The severity of the event maythen be used when determining an insurance premium discount of thedriver.

Note that a driver's safety score will change over time based on his orher driving habits. FIG. 12 is an example of a safety score display 1200that might be provided to a driver according to some embodiments. Inparticular, the display 1200 includes a graph 1210 showing the driverssafety score over a particular period of time (e.g., over the last monthor year). According to some embodiments, a driver may select the periodof time depicted on the graph 1210. Such a safety score display 1200 mayencourage a driver to improve his or her safety score and become a lessrisky driver.

An insurance premium discount may be based at least in part ontelematics data, a driver's safety score, and/or safety events thatoccur over time. According to some embodiment, a final discount valuemay not be determined until telematics data has been collected for apredetermined period of time and/or a predetermined number of miles.Even before the final discount value is determined, a likely discountvalue might be calculated based on a driver's known driving habits. Forexample, during a trial or initial period, a likely discount value mightbe calculated based on safety events that have occurred during the trialperiod. FIG. 13 illustrates a likely discount display 1300 according tosome embodiments. In particular, the display 1300 includes a currentmost likely discount 1310 calculated based on the existing telematicsdata that has been collected for that driver. Moreover, an upper likelydiscount 1320 and lower likely discount 1330 may also be displayed(e.g., there might be a 90% chance that the driver's final discount willnot exceed the upper likely discount 1320). Note that as more telematicsdata is collected over time, the upper and lower likely discounts 1320,1330 might converge until, at the end of a trial period, the finalpremium discount is actually computed for the driver.

According to some embodiments, an initial insurance premium discount maybe provided to a driver while telematics data is collected. FIG. 14 isan illustration 1400 of how an insurance premium might change over timeaccording to some embodiments. A baseline insurance premium associatedwith what a driver would pay if he or she did not participate in atelematics program is represented by a dashed line 1410 in FIG. 14 alongwith a solid line 1420 representing his or her actual premium. After thedriver agrees to participate in the program, telematics data iscollected during a pre-determined period of time 1430 (e.g., threemonths). During this time, the driver's insurance premium is reduced byan initial discount amount. After the pre-determined period of time1430, a final discount amount is determined and applied to his or herinsurance premium (and the final amount might be more or less than theinitial discount depending on his or her driving habits).

It may be difficult for a driver to predict or understand exactly howhis or her driving habits will adjust a safety score or premium discountvalue. According to some embodiments, a telematics calculator may beprovided for a driver to reduce this problem. For example, FIG. 15 is anexample of a telematics calculator 1500 display according to someembodiments. The telematics calculator 1500 includes an entry box 1510where a user can enter a predicted number of hard brake events that heor she expects will occur each week. The calculator 1500 also displayshow many hard brake events are currently occurring each week based onthe collected telematics data. Similarly, the driver may enter how manyspeeding events he or she predicts will occur. After entering thesevalues, the driver may activate a “calculate” icon 1520 causing thesystem to display a predicted score and/or premium discount value (orany other insurance benefit) based on the predicted hard brake andspeeding events. In this way, a driver may be encouraged to reduce thesetypes of events and improve his or her driving habits.

As another example, FIG. 16 is a telematics calculator 1600 where adriver can predict safety events of various severity or intensitylevels. In the example of FIG. 16, a driver predicts how many “high,”“medium,” and “low” intensity hard brake events will occur each week.According to other embodiments, a graphical representation 1610 may beused to reflect the entered information and/or may be used instead bythe driver to enter information (e.g., by rotating a gauge or dial).Based on this information, the calculator 1600 may generate and displaya predicted score and/or discount value.

According to other embodiments, a driver might enter a desired score orpremium discount value. For example, FIG. 17 is an example of aninsurance discount calculator 1700 in accordance with some embodimentsdescribed herein. The calculator 1700 may receive from a driver adesired premium discount via a sliding scale 1710 (e.g., in the exampleof FIG. 17 the driver is interested in receiving a 10% discount). Basedon the desired discount, the calculator 1700 generates a number ofsafety events for various types of events and/or various levels ofseverity. For example, the calculator 1700 might indicate that 5 highintensity hard brake events should be experienced per week in order forthe driver to receive a 10% discount. The calculator 1700 may be, forexample, associated with a web page, a smartphone application, and/or akiosk and may encourage drivers to adopt less risky driving habits.

The processes described herein may be performed by any suitable deviceor apparatus. FIG. 18 is one example of an insurance platform 1800according to some embodiments. The insurance platform 1800 may be, forexample, associated with the system 108 of FIG. 1. The insuranceplatform 1800 comprises a processor 1810, such as one or morecommercially available CPUs in the form of one-chip microprocessors,coupled to a communication device 1820 configured to communicate via acommunication network (not shown in FIG. 18). The communication device1820 may be used to communicate, for example, with one or more remotevehicles or third party services. The insurance platform 1800 furtherincludes an input device 1840 (e.g., a mouse and/or keyboard to enterinsurance discount information) and an output device 1850 (e.g., acomputer monitor to display aggregated insurance reports and/or resultsto an administrator).

The processor 1810 also communicates with a storage device 1830. Thestorage device 1830 may comprise any appropriate information storagedevice, including combinations of magnetic storage devices (e.g., a harddisk drive), optical storage devices, and/or semiconductor memorydevices. The storage device 1830 stores a program 1812 and/or scoringsystem 1814 for controlling the processor 1810. The processor 1810performs instructions of the programs 1812, 1814, and thereby operatesin accordance with any of the embodiments described herein. For example,the processor 1810 may receive telematics data from a vehicle. Theprocessor 1810 may also analyze the telematics data, and/or transmitdiscount information to a potential entity to be insured based at leastin part on a computed risk score.

Referring again to FIG. 18, the programs 1812, 1814 may be stored in acompressed, uncompiled and/or encrypted format. The programs 1812, 1814may furthermore include other program elements, such as an operatingsystem, a database management system, and/or device drivers used by theprocessor 1810 to interface with peripheral devices.

As used herein, information may be “received” by or “transmitted” to,for example: (i) the insurance platform 1800 from another device; or(ii) a software application or module within the insurance platform 1800from another software application, module, or any other source.

In some embodiments (such as shown in FIG. 18), the storage device 1830stores an underwriting database 1860 and/or a telematics database 1900.An example of a database that may be used in connection with theinsurance platform 1800 will now be described in detail with respect toFIG. 19. Note that the database described herein is only one example,and additional and/or different information may be stored therein.Moreover, various databases might be split or combined in accordancewith any of the embodiments described herein.

Referring to FIG. 19, a table is shown that represents the telematicsdatabase 1900 that may be stored at the insurance platform 1800according to some embodiments. The table may include, for example,entries identifying users, drivers, or vehicles. The table may alsodefine fields 1902, 1904, 1906, 1908, 1910 for each of the entries. Thefields 1902, 1904, 1906, 1908, 1910 may, according to some embodiments,specify: a driver identifier 1902, a policy identifier 1904, safetyevents 1906, dates and times 1908, and locations 1910. The informationin the telematics database 1900 may be created and updated, for example,based on information received from a vehicle sensor.

The driver identifier 1902 may be, for example, a unique alphanumericcode identifying a customer or potential customer (e.g., a person orbusiness). The policy identifier 1904 might represent an insuranceproduct that may be offered to the user associated with the driveridentifier 1902. The safety events 1906 might indicate a type of safetyevent and/or a severity of the safety event. The date and time 1908might indicate when the safety event occurred and the location 1910might indicate where the safety event occurred (e.g., a latitude andlongitude associated with the safety event). The information in thetelematics database 1900 may then be used to display icons or otherindications on a map display.

The following illustrates various additional embodiments of theinvention. These do not constitute a definition of all possibleembodiments, and those skilled in the art will understand that thepresent invention is applicable to many other embodiments. Further,although the following embodiments are briefly described for clarity,those skilled in the art will understand how to make any changes, ifnecessary, to the above-described apparatus and methods to accommodatethese and other embodiments and applications.

Although specific hardware and data configurations have been describedherein, not that any number of other configurations may be provided inaccordance with embodiments of the present invention (e.g., some of theinformation associated with the databases described herein may becombined or stored in external systems).

The present invention has been described in terms of several embodimentssolely for the purpose of illustration. Persons skilled in the art willrecognize from this description that the invention is not limited to theembodiments described, but may be practiced with modifications andalterations limited only by the spirit and scope of the appended claims.

What is claimed is:
 1. A system for displaying telematics data to a driver of a vehicle, the system comprising: a computer memory storing data indicative of telematics data received from a sensor within a vehicle, the telematics data comprising geo-position information of the vehicle and vehicle kinematics data; and a processor in communication with the memory, wherein the processor is configured for: identifying, based on the stored telematics data received from the sensor within the vehicle, safety events involving the vehicle, the safety events comprising one or more of deceleration above a threshold, acceleration above a threshold, turning above a threshold, speeding above a threshold and lane change speed above a threshold, and for each of the safety events involving the vehicle, locations of the safety events locations based on the data indicative of the telematics data, receiving data indicative of safety events associated with other drivers identified based on telematics data received from sensors within vehicles of the other drivers and locations of safety events identified based on telematics data received from sensors within the vehicles of the other drivers, and causing to be displayed to the driver indications of the identified safety events involving the vehicle on a map display along with indications of one or more of the safety events associated with the other drivers.
 2. The system of claim 1, wherein the identified safety events are associated with a plurality of different event types, and further comprising: receiving, from the driver, a selection of a particular event type, wherein only indications of the safety events associated with that particular event type are displayed to the driver on the map display.
 3. The system of claim 1, wherein the identified safety events are associated with event dates, and further comprising: receiving, from the driver, a date range, wherein only indications of the safety events having event dates within the date range are displayed to the driver on the map display.
 4. The system of claim 1, wherein the identified safety events are associated with a plurality of different event severities, and further comprising: receiving, from the driver, a selection of a particular event severity, wherein only indications of the safety events associated with that particular event severity are displayed to the driver on the map display.
 5. The system of claim 1, wherein at least some safety events are associated with: (i) times of day associated with driving, (ii) velocities associated with driving, (iii) distances associated with driving, (iv) weather information, (v) traffic information, and (vi) deceleration events.
 6. The system of claim 1, further comprising: receiving, from the driver, a filtering characteristic, wherein only safety events associated with other drivers having the filtering characteristic are displayed on the map display.
 7. The system of claim 6, wherein the filtering characteristic is associated with at least one of: (i) age, (ii) driving experience, (iii) vehicle type, (iv) gender, or (v) residence.
 8. The system of claim 1, wherein the data indicative of telematics data is received by an insurance company from a third party service.
 9. The system of claim 8, wherein the processor is further to receive from the third party service at least some data indicative of telematics data that does not identify particular drivers or vehicles.
 10. The system of claim 1, wherein the processor is further configured for: outputting an indication of a suggested driving modification.
 11. The system of claim 10, wherein the suggested driving modification is output to at least one of: (i) a parent of the driver, and (ii) an employer of the driver.
 12. The system of claim 1, wherein information about safety events is automatically forwarded to at least one of: (i) a community improvement resource, or (ii) a social network site.
 13. A computerized method for displaying telematics data to a driver of a vehicle, the method comprising: receiving, by a processor, data indicative of telematics data collected from a sensor coupled to the vehicle, wherein the telematics data includes geo-position information and kinematics data of the vehicle; identifying, by the processor, based on the stored telematics data received from the sensor within the vehicle, safety events involving the vehicle, the safety events comprising one or more of deceleration above a threshold, acceleration above a threshold, turning above a threshold, speeding above a threshold and lane change speed above a threshold, and locations of the safety events involving the vehicle identified based on the telematics data; receiving, by the processor, data indicative of safety events associated with other drivers identified based on telematics data received from sensors within vehicles of the other drivers and locations of the safety events identified based on telematics data received from sensors within vehicles of the other drivers; and causing to be displayed to the driver indications of the safety events involving the vehicle on a map display along with indications of one or more of the safety events associated with the other drivers.
 14. The method of claim 13, wherein the identified safety events are associated with a plurality of different event types, and further comprising: receiving, from the driver, a selection of a particular event type, wherein only indications of the safety events associated with that particular event type are displayed to the driver on the map display.
 15. The method of claim 13, wherein the identified safety events are associated with event dates, and further comprising: receiving, from the driver, a date range, wherein only indications of the safety events having event dates within the date range are displayed to the driver on the map display.
 16. The method of claim 13, wherein the identified safety events are associated with a plurality of different event severities, and further comprising: receiving, from the driver, a selection of a particular event severity, wherein only indications of the safety events associated with that particular event severity are displayed to the driver on the map display.
 17. The method of claim 13, wherein at least some safety events are associated with: (i) times of day associated with driving, (ii) velocities associated with driving, (iii) distances associated with driving, (iv) weather information, (v) traffic information, and (vi) deceleration events.
 18. The method of claim 13, further comprising: displaying to the driver indications of safety events associated with other drivers on the map display.
 19. A non-transitory computer readable medium having stored therein instructions that, upon execution, cause a computer to perform a method for displaying telematics data to a driver of a vehicle, the method comprising: receiving, by a processor, data indicative of telematics data collected from a sensor coupled to the vehicle, wherein the telematics data includes geo-position information and kinematics data of the vehicle; identifying, by the processor, based on the stored telematics data received from the sensor within the vehicle, safety events, the safety events comprising one or more of deceleration above a threshold, acceleration above a threshold, turning above a threshold, speeding above a threshold and lane change speed above a threshold, and locations of the identified safety events based on the telematics data; receiving, by the processor, data indicative of safety events associated with other drivers identified based on telematics data received from sensors within vehicles of the other drivers and locations of the safety events identified based on telematics data received from sensors within vehicles of the other drivers; and causing to be displayed to the driver indications of the safety events involving the vehicle on a map display along with indications of one or more of the safety events associated with the other drivers.
 20. The medium of claim 19, wherein the identified safety events are associated with a plurality of different event types, and the method further comprises: receiving, from the driver, a selection of a particular event type, wherein only indications of the safety events associated with that particular event type are displayed to the driver on the map display.
 21. The medium of claim 19, wherein the identified safety events are associated with event dates, and the method further comprises: receiving, from the driver, a date range, wherein only indications of the safety events having event dates within the date range are displayed to the driver on the map display.
 22. The medium of claim 19, wherein the identified safety events are associated with a plurality of different event severities, and the method further comprises: receiving, from the driver, a selection of a particular event severity, wherein only indications of the safety events associated with that particular event severity are displayed to the driver on the map display.
 23. The medium of claim 19, wherein at least some safety events are associated with: (i) times of day associated with driving, (ii) velocities associated with driving, (iii) distances associated with driving, (iv) weather information, (v) traffic information, and (vi) deceleration events. 